Skip to content

VS Code tests: split smoke tests and DAP end-to-end suites for local …#568

Open
midenotch wants to merge 2 commits intoTimi16:mainfrom
midenotch:code-test-split
Open

VS Code tests: split smoke tests and DAP end-to-end suites for local …#568
midenotch wants to merge 2 commits intoTimi16:mainfrom
midenotch:code-test-split

Conversation

@midenotch
Copy link
Contributor

Close: #539

Separated the VS Code extension suites so smoke and DAP E2E are independently targetable.

The new structure lives in [suites.ts], with thin entrypoints at [runSmokeTest.ts]and [runDapE2E.ts]. The old combined runner is now just a wrapper in [runTest.ts].

Local and CI selectivity are wired through [package.json] and [.github/workflows/ci.yml] and the public test commands are documented in [README.md]

I also made a minimal syntax repair in [debuggerProcess.ts] so TypeScript could get past an unrelated parser break, but full verification is still blocked by pre-existing extension compile errors in that file and [adapter.ts]. Because of that, npm run test:smoke and npm run test:dap-e2e could not be fully executed yet, and cargo build --bin soroban-debug was also blocked by sandboxed network access to crates.io.

@drips-wave
Copy link

drips-wave bot commented Mar 25, 2026

@midenotch Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@midenotch
Copy link
Contributor Author

Done, Close: #568

@Timi16
Copy link
Owner

Timi16 commented Mar 25, 2026

Done, Close: #568

Resolve conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

VS Code tests: split smoke tests and DAP end-to-end suites for local and CI selectivity

2 participants